Multiple server automation for secure cloud reconciliation

ABSTRACT

In various example embodiments, a system and method for automated data reconciliation processing is presented. The system receives a data movement request with a first status indicator and appends a unique request code to the data movement request. The system causes presentation of the data movement request at a client device and receives a movement response from a second server via a network. The system modifies the first status indicator of the data movement request to a second status indicator to provisionally reflect the receipt of the movement response and verifies the indication of movement from a receiving entity.

TECHNICAL FIELD

The present disclosure generally relates to automating multiple serversto perform secure cloud reconciliation. More specifically, to systemsand methods for automated reconciliation of requests via data fromvarious servers.

BACKGROUND

A sending entity receives a request for data from a receiving entity viaemail, on paper, or through an online service (via online servers). Suchdata requests between entities are often performed by third parties and,technically, are often performed using an electronic system.

This process, once considered to be efficient and innovative, is nowoften a manual way to handle such transfers, particularly in the contextof a cloud data management system that must work with millions of datatransfers from countless entities simultaneously. To make a transfer,the sending entity connects to a server, manually enters the transferdetails, and submits the transfer request. The relevant transfer is madeto the receiving entity's server from the sending entity's server.

To make a similar data transfer via a third party, the sending entityconnects to a server associated with the third party, enters thetransfer details, and submits the transfer request. The relevant data istransferred from the sending entity's server to the third party server.The third party server then transfers said information to the receivingentity's server.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not of limitationin the figures of the accompanying drawings.

FIG. 1 is a block diagram depicting an example single ledger accountingplatform, according to some embodiments.

FIG. 2 is a block diagram depicting an example accounting applicationframework for the accounting platform, according to some embodiments.

FIG. 3 is a block diagram depicting an example hosting infrastructurefor the accounting platform, according to some embodiments.

FIG. 4 is a block diagram depicting an example data center system of theaccounting platform, according to some embodiments.

FIG. 5 is a block diagram depicting an example request reconciliationsystem of the data management system, according to some exampleembodiments.

FIG. 6 is a block diagram depicting an example client device foraccessing the data management system, according to some embodiments.

FIG. 7 is a block diagram depicting the flow of data between entitiesfacilitating data movement and reconciliation, according to someembodiments.

FIG. 8 is a flowchart of an example method for facilitating datamovement and reconciliation, according to some embodiments.

FIG. 9 is a flowchart of an example method for facilitating datamovement request processing and reconciliation, according to someembodiments.

FIG. 10 is a block diagram of a machine in the example form of acomputer system within which a set of instructions, for causing themachine to perform any one or more of the methodologies discussedherein, may be executed, according to some embodiments.

DETAILED DESCRIPTION

Example systems and methods to facilitate data movement andreconciliation are described. In the following description, for purposesof explanation, numerous specific details are set forth in order toprovide a thorough understanding of example embodiments. It will beevident, however, to one skilled in the art that the present technologymay be practiced without these specific details.

The technology described herein provides data and message transmissionbetween a one or more servers across differing domains to coordinatemultiple parties into automated reconciliation of requests, dataprovisioning, and responses as part of a single transaction. The datarequest, provisioning, and reconciliation of responses may form all orpart of a reconciliation system. In some embodiments, as describedbelow, the reconciliation system may be used in conjunction withadditional software or systems to provide one or more of themethodologies described herein for requesting, provisioning, andreconciling data transfers across distinct domains

In some example embodiments, the technology described herein providesonline (i.e., cloud based) software services to businesses with featuressuch as a data transfer and reconciliation mechanism available to abusiness's customers. The data transfer and reconciliation mechanism maydrive data elements through a designated server rather than secondserver of the second domain (e.g., credit card transaction processors,PayPal, and so on), and perform subsequent automatic recording of thatdata element matched to the original data movement request within thereconciliation system. A data movement request may be understood as astatement of data elements for which a specified user or server is toperform a predetermined actions with respect to the data element.

For example, the methods and systems described herein may enabletransfer and reconciliation of payments between users where the paymentsare associated with data movement requests (i.e., payment orcompensation requests and invoices). The payment initiator may generatean invoice and transmit the invoice to a second server of the seconddomain for transacting payment between the payment initiator (e.g.,payee) and the payer. The payer may be presented with the complete orpartial invoice during a network-based communication session (e.g.,online banking session), either with the payer's bank or the secondserver of the second domain. The payer may initiate a paymenttransaction, handled between the second server of the second domain, thefirst entity, and the payee's bank. One or more of the first entity, thesecond server of the second domain, and the second entity providenotifications and invoice payment updates to the data management systemwhich determines reconciliation of the payment and notification to thepayee and payer.

The information may be sent from the payment initiator to theinstitution via the customer (e.g., the payer). For example, theencrypted data may be sent from a web site of the payment initiator to aweb browser of the customer running on a customer device. After thepayment has been initiated by the institution, a confirmation may besent to the customer, the payment initiator, the business, or anysuitable combination thereof.

FIG. 1 is a block diagram depicting an example single ledger datamanagement system 100. In some embodiments, the data management system100 may be a single ledger accounting system 100 providing accountingtools to a particular entity managing accounting for one or morebusinesses. The example single ledger accounting system 100 may includea practice studio 110 that allows an entity to manage one or morebusinesses and an organization access module 150 that provides abusiness with tools for managing accounting data for that particularbusiness. The practice studio 110 may include a practice staffmanagement module 114, an online training module 116, a practicemanagement module 118, a partner resources module 120, a report packssetup module 122, and a work papers module 124. The practice studio 110may be in communication with core features 130. The core features 130may include an data provision module 132, a community module 134, asubscription management module 136, a notifications center module 138, auser profile management module 140, and a login module 142. Theorganization access module 150 may be in communication with the corefeatures 130. The practice studio 110 and core features may be accessedby an entity using a login module 142.

As shown in FIG. 1, features of the accounting system 100 are dividedinto three areas based on the target user. The features of the practicestudio 110 provide a suite of tools for accountants to interact withtheir clients and manage their practices. The core features 130 providethe core functionality and user tools common to both accountants andbusinesses. The organization access module 150 provides a user interfacefor individual businesses to access their data.

Practice studio 110 is the central login for accountants. For example,an accountant with multiple clients, each of which is a small business,can login using practice studio 110 and gain access to the accountingdata for the clients, messages from the clients, and so on.

The practice staff management module 114 provides the ability for themanager of an accounting practice to control settings for the staff ofthe practice. For example, some staff members may have read-only accessto data for certain clients, some staff members may have read-writeaccess for certain clients, some staff members may be able to modify theaccess permissions for other staff members, and so on.

The online training module 116 provides training for accountants andtheir staff. In some cases, the provided training includes one or morevideo presentations and one or more online tests. Notification ofpassing a test at completion of a training may be provided. For example,a staff member may take a training course and, upon successfulcompletion, the accountant supervising the staff member may receive anotification of the successful completion.

The practice management module 118 provides services for accountants.Access to the features provided by the practice management module 118may be limited to accountants having a predetermined partner level withthe data management platform provider. For example, access to thepractice management module 118 may be limited to accountants at silverlevel or above. The services provided by the practice management module118 may include workflow tools, customer relationship management (CRM)tools, lead generation tools, job management tools, data movementrequest generation tools, and so forth.

The partner resources module 120 provides information regardingthird-party partners. For example, a third party may provide tools thatinteract with the system to provide useful functionality beyond that ofthe system alone. The user can access the partner resources module 120to learn about available third-party tools. For example, links tothird-party websites, documentation, videos, and search tools may all beprovided.

The report packs setup module 122 provides tools to allow accountants tocreate and generate standardized sets of reports. For example, a profitand loss statement and quarterly report could both be added to a pack.The accountant would then be able to easily generate both reports forany selected client, or generate the reports for every client.

The work papers module 124 provides tools for accountants tointeractively create financial reports. For example, an accountant canenter known data for a client into the work paper, and then send thework paper to the client with an indication of data needed from theclient. After the client enters the missing data into the work paper,the accountant can complete the report.

The core features 130 includes modules that are used both by accountantsand organizations. The data provision module 132 provides the generalledger for organizations. The general ledger may be integrated with theorganization's payroll, bypassing the separate step of entering payrolldata into the general ledger each pay period. The data provision module132 accesses banking data for each client business. The banking data maybe imported into either through a bank feed or a user- oraccountant-created document. The data provision module 132 may alsocommunicate with third-party tools via an application protocol interface(API).

The community module 134 provides a forum through which users cancommunicate. For example, a user with a question may post a topic in theforum and later receive a helpful response from another user.Information taken from the user profile (e.g., the user profile managedvia the user profile management module 140) may appear along with forumposts by the user. For example, a user name, an image of the user, andthe user's status as an accountant or member of an organization may eachbe shown.

The subscription management module 136 allows a user to configure one ormore billing accounts for each organization using the system. The systemmay periodically charge a subscription fee for access (e.g., a monthlyor annual subscription fee). The subscription fee may be automaticallydeducted from the one or more billing accounts. Modules performingvarious functions of the subscription management module 136, withrespect to direct bank transactions are described with more detail belowin FIG. 5.

The notifications center module 138 provides notifications to users. Forexample, users may send messages to each other, which appear asnotifications. Notifications may also be created by the system (e.g., bydata provision module 132) based on events. For example, a minimumaccount balance for a particular bank account may be set by a user viathe data provision module 132. When the balance for that bank accountdrops below the minimum account balance, a notification can be generatedby the system informing the user.

The user profile management module 140 allows a user to manage theprofile of the user's organization and the profiles of others based onpermission settings. For example, an accountant may have permission tomanage the profiles of the accountant's clients. The profile may includepublic-facing information such as a business name and address.

The login module 142 verifies the identity of a user logging into thesystem (e.g., via user name and password). Based on the user's identity,a user interface is presented that includes a list of organizations thata user has access to. For most small business clients, the list willconsist of a single organization.

The organization access module 150 accesses the core features 130 for asingle organization. The organization access module 150 presents, afteruser verification by the login module 142, a user interface with optionsfor a single organization without the additional features used only bythe practice studio 110.

FIG. 2 is a block diagram depicting an example data managementapplication framework 200 for the data management platform. The datamanagement application framework 200 may be an end-to-end webdevelopment framework enabling a “software as a service” (SaaS) product.The data management application framework 200 may include a hypertextmarkup language (HTML) and/or JavaScript layer 210, ASP.NetModel-View-Controller (MVC) 220, extensible stylesheet languagetransformations (XSLT) 230, construct 240, services 250, objectrelational model 260, and database 270.

The HTML and/or JavaScript layer 210 provides client-side functionality,such as UI generation, receipt of user input, and communication with aserver. The client-side code may be created dynamically by the ASP.NETMVC 220 or the XSLT 230. Alternatively, the client-side code may bestatically created or dynamically created using another server-sidetool.

The ASP.Net MVC 220 and XSLT 230 provide server-side functionality, suchas data processing, web page generation, and communication with aclient. Other server-side technologies may also be used to interact withthe database 270 and create an experience for the user.

The construct 240 provides a conduit through which data is processed andpresented to a user. For example, the ASP.Net MVC 220 and XSLT 230 canaccess the construct 240 to determine the desired format of the data.Based on the construct 240, client-side code for presentation of thedata is generated. The generated client-side code and data forpresentation is sent to the client, which then presents the data.

The services 250 provide reusable tools that can be used by the ASP.Net220, the XSLT 230, and the construct 240 to access data stored in thedatabase 270. For example, aggregate data generated by calculationsoperating on raw data stored in the database 270 may be made accessibleby the services 250.

The object relational model 260 provides data structures usable bysoftware to manipulate data stored in the database 270. For example, thedatabase 270 may represent a many-to-one relationship by storingmultiple rows in a table, with each row having a value in common. Bycontrast, the software may prefer to access that data as an array, wherethe array is a member of an object corresponding to the common value.Accordingly, the object relational model 260 may convert the multiplerows to an array when the software accesses them and perform the reverseconversion when the data is stored.

FIG. 3 is a block diagram depicting an example hosting infrastructure300 for the data management platform. The platform may be implementedusing one or more pods 310. Each pod 310 includes application servervirtual machines 320 (shown as application server virtual machines320A-320C in FIG. 3) that are specific to the pod 310 as well asapplication server virtual machines (VMs) that are shared between pods310 (e.g., the internal services VM 330 and the application protocolinterface VM 340). The application server virtual machines 320-340communicate with clients and third-party applications via a webinterface or an API. The application server virtual machines 320-340 aremonitored by application hypervisors 350. An internal firewall 360ensures that only approved communications are allowed between a databasehypervisor 370 and the publically-accessible virtual machines 320-340.The database hypervisor 370 monitors the primary SQL servers 380A and380B. The primary SQL servers 380A and 380B access the shared storagelayer 450A or 450B (shown in FIG. 4) to read and write data generated byor used by the application server virtual machines 320-340. Theredundant SQL servers 390A and 390B provide backup functionality for theprimary SQL servers 380A and 380B, respectively.

The virtual machines 320-340 can be implemented using Windows 2008 R2,Windows 2012, or another operating system. The application and supportservers supporting the virtual machines 320-340 can be built usingspares for redundancy. The support servers can be shared across multiplepods 310. The application hypervisors 350, internal firewall 360, anddatabase hypervisor 370 may span multiple pods 310 within a data center.In some example embodiments, each primary SQL server 380 and redundantSQL server 390 is configured to support 30,000-45,000 organizations.Accordingly, in embodiments using two such server pairs per pod 310, thepod capacity is 60,000-90,000 organizations. The redundant SQL servers390 may take advantage of the “always on” resilience feature of SQL2012.

FIG. 4 is a block diagram depicting an example data center system 400 ofthe data management platform interacting with other systems over anetwork. The primary data center 410 services customer requests and isreplicated to the secondary data center 420. The secondary data center420 may be brought online to serve customer requests in case of a faultin the primary data center 410. The primary data center 410 communicatesover a network 455 with data flow server 460, third party server 470,client device 480, and client device 490. The data flow server 460provides banking data (e.g., via the data flow application 465). Thethird party server 470 is running third party application 475. Clientdevices 480 and 490 interact with the primary data center 410 using webclient 485 and programmatic client 495, respectively.

Within each data center 410 and 420, a plurality of pods, such as thepod 310 of FIG. 3, are shown. The primary data center 410 is showncontaining pods 440A-440D. The secondary data center 420 is showncontaining pods 440E-440H. The applications running on the pods of theprimary data center are replicated to the pods of the secondary datacenter. For example, EMC replication (provided by EMC Corporation) incombination with VMWare site recovery manager (SRM) may be used for theapplication layer replication. The database layer handles replicationbetween the storage layer 450A of the primary data center and thestorage layer 450B of the secondary data center. Database replicationprovides database consistency and the ability to ensure that alldatabases are at the same point in time.

The data centers 410 and 420 use load balancers 430A and 430B,respectively, to balance the load on the pods within each data center.The data centers 410 and 420 can be created using identical hardware toensure that the performance of the secondary data center 420 is the sameas the performance of the primary data center 410. The storage layer450A and 450B may be implemented using one or more storage area networkssuch as the VNX storage area networks from EMC.

The data flow server 460 interacts with the primary data center 410 toprovide bank records for bank accounts of the client. For example, theclient may provide account credentials to the primary data center 410,which the primary data center 410 uses to gain access to the accountinformation of the client. The data flow server 460 can provide thebanking records to the primary data center 410 for later reconciliationby the client using the client device 480 or 490.

The third party server 470 may interact with the primary data center 410and the client device 480 or 490 to provide additional features to auser of the client device 480 or 490. For example, a user may authorizethe third party server 470 to access the user's data stored in theprimary data center 410. The third party application 475 of the thirdparty server 470 may use the user's data to generate reports, providemacros, or otherwise improve the user's ability to access or manipulatethe user's data. The third party application 475 may communicate withthe primary data center 410 via the network 455 using an API. The thirdparty application 475 may communicate with the client device 480 or 490using a web or programmatic interface.

FIG. 5 is a block diagram 500 illustrating components of an datareconciliation system 505 suitable for presentment of data movementrequests, data provisioning, and reconciliation of the data movementrequest with transaction records (e.g., statements) of an associatedserver (i.e., an institution). As shown in FIG. 5, the datareconciliation system 505 is a part of the data provision module 132,according to some example embodiments. The data reconciliation system505 is shown as including a receiver module 510, a code managementmodule 520, a movement module 530, a status module 540, a verificationmodule 550, a notification module 560, a presentation module 570, and acommunication module 580 all configured to communicate with each other(e.g., via a bus, shared memory, or a switch). Any one or more of themodules described herein may be implemented using hardware (e.g., aprocessor of a machine) or a combination of hardware and software. Forexample, any module described herein may configure a processor toperform the operations described herein for that module. Moreover, anytwo or more of these modules may be combined into a single module, andthe functions described herein for a single module may be subdividedamong multiple modules. Furthermore, according to various exampleembodiments, modules described herein as being implemented within asingle machine, database, or device may be distributed across multiplemachines, databases, or devices.

The receiver module 510 receives data indicative of invoices,transaction records (e.g., responses to batch data movement requests),and other data transmitted to the data reconciliation system 505. Thereceiver module 510 passes requests or instructions relating to the datamovement requests (e.g., invoices) and data transaction records to othermodules of the data reconciliation system 505. The receiver module 510may pass the requests, responses, and instructions to the other modulesusing the communication module 580. The receiver module 510 is ahardware-implemented module or a module implemented by a combination ofhardware and software (e.g., hardware configured by software to performvarious functions). An example embodiment of components included in oraccessed by the receiver module 510 is described with respect to FIG.10. Functions of the receiver module 510 are discussed in further detailbelow.

The code management module 520 receives data indicative of data movementrequests from the receiver module 510 and appends request codes to thedata movement requests. In some example embodiments, the code managementmodule 520 generates unique request codes (e.g., unique invoice codesidentifying an invoice) prior to appending the request codes to the datamovement requests. The code management module 520 may pass the datamovement request with appended request code to one or more of the statusmodule 540, the verification module 550, and the presentation module 570using the communication module 580. In some example embodiments, thecode management module 520 may store the data movement request andappended request code in a data structure (e.g., data table) within thedatabase 270 for access and modification by one or more of the modulesof the data reconciliation system 505. The code management module 520can be a hardware implemented module or a combination of hardware andsoftware implemented module. An example embodiment of componentsincluded in or accessed by the code management module 520 is describedwith respect to FIG. 10.

The movement module 530 requests and receives movement responses (e.g.,indications of payment) during network based communications sessions(e.g., a network-based banking session). For example, in someembodiments where the reconciliation system 505 is reconciling payments,the movement module 530 requests and receives indications of paymentduring the network-based communications session. The movement module 530may store the movement responses in the database 270 for access by othermodules. In various embodiments, the stored movement responses areassociated within the database 270 with user profile information and adata movement request for which the movement request is a response. Themovement module 530 is a hardware implemented module or a combination ofhardware and software implemented module. An example embodiment ofcomponents included in or accessed by the movement module 530 isdescribed with respect to FIG. 10.

The status module 540 identifies and modifies status indicators withininvoices to reflect changes in status of movement for the data movementrequest. The status module 540 accesses and modifies the statusindicators of the data movement request stored in the database 270. Thestatus module 540 may be a hardware implemented module or a combinationof hardware and software implemented module. An example embodiment ofcomponents included in or accessed by the status module 540 is describedwith respect to FIG. 10.

The verification module 550 verifies movement responses from recipientsand reconciles data movement requests with data movements passing amongservers across domains (e.g., institutions). In various exampleembodiments, the verification module 550 uses the communication module580 to transmit batch data movement requests and receive movementnotifications including statements of data movement (e.g., transactionrecords within a date range) from servers across one or more domains(e.g., institutions) associated with users of the data management system100 in order to verify transaction data relating to movement responsesusing the data reconciliation system 505 and reconcile data movementrequests with the transaction data. The verification module 550 can be ahardware implemented module or a combination of hardware and softwareimplemented module. An example embodiment of components included in oraccessed by the verification module 550 is described with respect toFIG. 10.

The notification module 560 generates notifications of payment for thedata reconciliation system 505. In various example embodiments, thenotification module 560 generates presentation notifications verifyingpresentation of the data movement request and request code at a clientdevice (e.g., the client device 480 or 490), and various other functionsdescribed herein. The notification module 560 can be a hardwareimplemented module or a combination of hardware and software implementedmodule. An example embodiment of components included in or accessed bythe notification module 560 is described with respect to FIG. 10.

The presentation module 570 causes presentation of data movementrequests and transaction detail information (e.g., statement responses,account information, payment information, and reconciliationinformation) at client devices (e.g., the client device 480 or 490). Thepresentation module 570 can generate a set of user interface elements,screens, frames, or the like for presentation at client devices. Thepresentation module 570 causes presentation of data movement requestsand transaction detail information by transmitting data representativeof the data movement requests and the transaction detail information tothe client device, via the communication module 580. The presentationmodule 570 can be a hardware implemented module or a combination ofhardware and software implemented module. An example embodiment ofcomponents included in or accessed by the presentation module 570 isdescribed with respect to FIG. 10.

The communication module 580 may facilitate communication among thereceiver module 510, the code management module 520, the movement module530, the status module 540, the verification module 550, thenotification module 560, the presentation module 570, the client device480 or 490, third party server 470, and the data flow server 460. Insome embodiments, the communication module 580 facilitates or enablescommunication with a plurality of bank servers, with the data flowserver 460 among the plurality of bank servers. The communication module580 may enable communication among the modules and components describedherein via a bus, shared memory, a switch, or any other suitablecommunication mechanism or method. As such, the communication module 580may be a configured port, server, or other hardware device configured bysoftware or machine-executable instructions to perform one or more ofthe communications related methodologies described herein.

FIG. 6 is a block diagram illustrating components of a block diagram 600(e.g., representing a client device) suitable for mobile bankingreconciliation, according to some example embodiments. The client device480 (or 490) is shown as including a communication module 610, a displaymodule 620, an input module 630, and a reconciliation module 640,configured to communicate with each other (e.g., via a bus, sharedmemory, or a switch).

The communication module 610 may communicate with the primary datacenter 410, the third party server 470, the network 455, or any suitablecombination thereof. Information received via the communication module610 may be presented (e.g., displayed on a display device) via thedisplay module 620. Information may be selected or search queries may beentered by a user of the client device 480 (or 490).

A user interface is presented by the display module 620. The input fromthe user is detected by the input module 630. Commands received from theuser by the input module 630 may be communicated to the primary datacenter 410 by the communication module 610. The communication module 610may receive a response from the primary data center 410 that includes aset of banking records, a set of business records, associations betweenindividual banking records and individual business records that indicatereconciliation between those records, and other data, in anycombination.

The reconciliation module 640 can generate requests to the primary datacenter 410 to indicate that a banking record is reconciled by one ormore business records. The request can be communicated to the primarydata center 410 via the communication module 610, over the network 455.

FIG. 7 is a block diagram depicting the flow of data between entitiesfacilitating a transfer of funds, in an example embodiment. The entitiesinteracting within FIG. 7 are a first device 702 (e.g., a client device480 or 490 associated with a first user), a first entity 704, a secondserver of the second domain 706, second entity 708, the data managementsystem 100, and a second device 710 (e.g., a client device 480 or 490associated with a second user). In some instances, the first device 702is associated with a user of the data management system 100. In contextof FIG. 7, and the methodologies described herein, the first user,employing the first device 702 or any other suitable device, is thepaying party of the transaction billed by the second user, generating abill and transaction using the second device 710 or any other suitabledevice.

The first entity 704 is a institution associated with the first user orthe first device 702. As described herein, the first entity 704 is abank capable of performing network-based (e.g., online) transactions forand against an account of the first user. However, it should beunderstood that the first entity 704 may be any suitable institutionsuch as a bank, a credit union, a second server of the second domaindrawing on an associated payment account of the first user, or any otherinstitution. In some embodiments the payment account of the first useris associated with the first device 702 accessed through the firstdevice 702.

The second server of the second domain 706 is a network-based servicecapable of performing all or part of a payment transaction between twoinstitutions (e.g., the second entity 708 and the first entity 704). Invarious embodiments, the second server of the second domain 706 is athird party second server of the second domain (e.g., PayPal, CheckFree,an ACH system, etc.). However, it should be understood that, in someembodiments, the second server of the second domain 706 is affiliatedwith or a part of the first entity 704. In these embodiments,transactions, such as billing statements, transmitted to the secondserver of the second domain 706 are effectively transmitted to the firstentity 704.

The second entity 708 is a institution associated with the second user,and may be associated with the second user through a second useraccount. The second user may use the second device 710. In variousembodiments, the second entity 708 is a bank capable of performingnetwork-based (e.g., online) transactions for and against an account ofthe second user, a credit union, a second server of the second domaindrawing on an associated payment account (e.g., second user account) ofthe second user, or any other suitable institution. The second user is auser of the data management system 100 and may access the datamanagement system 100 using the second device 710.

As shown in FIG. 7, the second user may interact with the datamanagement system 100, using the second device 710, to enroll in one ormore service of the data management system 100, electronically presentbills (e.g., ebill) directly to a network enabled (e.g., online) bankaccount of the first user associated with the first device 702. Invarious embodiments, the data management system 100 enrolls second userby a registration function 712 exchanging information between the datamanagement system 100 and the second device 710. The registrationfunction 712 may create an account or otherwise associate the seconduser or the second device 710 with the data management system 100 togenerate identifiable information for the second user or the seconddevice 710 within the data management system 100. For example, theregistration function 712 may prompt the second user to enter, using thesecond device 710, an account name, a password, demographic information,financial information, contact information, and information relating togoods and services for which the second device 710 may generate datamovement requests or other records automatically or by interactionbetween the second user and the second device 710.

In various embodiments, in function 714, the data management system 100registers second user or the second device 710 with one or more of thefirst entity 704 and the second server of the second domain 706.Although function 714 is shown in FIG. 7 as extending between the datamanagement system 100 and the second server of the second domain 706, itshould be understood that the function 714 may similarly register thesecond user or second device 710 with the first entity 704. In someinstances, the function 714 registers the second user or second device710 with a plurality of institutions. For example, the data managementsystem 100, via the function 714, may register the second user or seconddevice 710 with a plurality of institutions with which the datamanagement system 100 is associated or who recognize the data managementsystem 100. In some instances, the data management system 100 registersthe second user or second device 710 automatically, without userinteraction from the second user via the second device 710 after thesecond user enrolls with the data management system 100 via the function712 using the second device 710. In some embodiments, completion of thefunction 712 causes the data management system to automatically performthe function 714 to register the second user or second device 710 withthe plurality of institutions.

After the second device 710 has interacted with the data managementsystem 100 via the function 712 to enroll the second user and the datamanagement system 100 has registered the second user or the seconddevice 710 by the function 714, the second device 710 may generateelectronic bills and transmit the electronic bills by the datamanagement system 100 to one or more of the plurality of institutions(e.g., the first entity 704 and the second server of the second domain706). Generation of an electronic bill is performed through billcreation function 720. The bill creation function 720 may includegeneration and presentment of a user interface (e.g., a set of userinterface screens) at the second device 710 to generate and transmit theebill to the first device 702 (e.g., a client device associated with thefirst user). For example, the second device 710 may present a set ofselectable user interface elements within a graphical user interfaceprompting or accepting input of various transaction data, such as itemor service information, purchase terms, purchase price, payerinformation, and other data which may form part of a transaction betweena merchant and a customer. In various embodiments, the data managementsystem 100 may automatically generate the ebill based on transactionspassed to the data management system 100 from the second device 710. Forexample, where the second user has an electronic commerce websitethrough which the first user makes a purchase using the first device702, the website may pass transaction data to one or more of the seconddevice 710 and the data management system 100. Receiving the transactiondata may trigger the data management system 100 to generate the ebillwithout further input or interaction by the second user.

The data management system 100 submits the ebill (e.g., an data movementrequest or invoice) generated via function 720 to the second server ofthe second domain 706 via function 722. In some instances, the datamanagement system 100 submits the ebill to the first entity 704,directly or through the second server of the second domain 706. Thesubmission of the ebill via function 722, as well as billing and paymentfunctions logged or conducted through the data management system 100 areaccounting transactions tracked by the data management system 100. Infunction 720 or prior to the function 720, the data management system100 generates a unique identifier and includes the unique identifierwithin the data movement request as a part of either a full or partialdata movement request presentment at the first device 702. In someembodiments, the data movement request is presented as a single datamovement request, while in some embodiments, a single data movementrequest may be divided and presented as multiple data movement requests(e.g., an invoice paid on an installment plan). In embodiments where thedata movement request is presented as multiple data movement requests,the multiple data movement requests may each receive a unique identifieror may each contain the same unique identifier.

The first device 702 may request ebills (e.g., data movement requests orinvoices) from the first entity 704 via a bill request function 724. Insome embodiments, the bill request function 724 is performed in responseto interactions between the first user operating the first device 702.The bill request function 724 may also be automated, such that the firstdevice 702 performs the bill request function 724 based on a scheduledtime or one or more monitored conditions. Monitored conditions mayinclude an email having an data movement request, operation of anapplication on the first device 702 in which a payment function of theapplication was used, accessing of a purchasing application on the firstdevice 702, accessing of a commerce website in a browser of the firstdevice 702, or any other monitored condition. In embodiments where thefirst device 702 requests ebills using the bill request function 724,the first user may be required to register (e.g., register the firstuser or register the first device 702) via function 726 to receiveebills from the second user generated by one or more of the seconddevice 710 and the data management system 100. The registration function726 may be performed similarly to the registration or enrollmentprocesses discussed above. In some instances, the registration function726 includes enrolling in an online banking service.

As shown in FIG. 7, the second server of the second domain 706 presentsthe ebill in a presentation function 728, after registration. In variousembodiments, the bill request function 724 is a function involving thedata management system 100 and the second server of the second domain706, where the data management system 100 has a preexisting relationshipwith the first entity 704 and the second server of the second domain 706as established via functions 712 and 714 described above. In someinstances, as shown in FIG. 7, the bill request function 724 is afunction of the first entity 704 performed during an onlinecommunication session between the first entity 704 and the first device702.

The first device 702 interacts with the first entity 704 to cause thefirst entity 704 to perform a payment function 730. As will be explainedin more detail below, the payment function 730 remits payment to thesecond entity 708 through the second server of the second domain 706. Aportion of the payment function 730 may be part of or trigger the datamanagement system 100 to reconcile accounts for the first user and thesecond user with respect to the payment and transmit notification of thereconciled accounts to one or more of the first device 702 and thesecond device 710. The payment function 730 causes the second server ofthe second domain 706 to transmit the payment and payment identification732 to the second entity 708.

Transmission of the payment and payment identification 732 to the secondentity 708 causes (e.g., triggers or includes) transmission of anotification of receipt 734 to the data management system 100. Thenotification of receipt includes the unique identifier, as well as apayment identifier generated in function 732. In various embodiments,the payment identifier is presented within transaction records of thesecond entity 708. The payment identifier may be one or more of, but notlimited to, ACH descriptors, generated check numbers, or previouslysupplied data movement request or unique identifier. In response toreceiving the notification of receipt 734, the data management system100 causes presentation of a notification of receipt 736 at the seconddevice 710. Matching the notification of receipt 736 to the uniqueidentifier for the transaction, the data management system 100 verifiesvia function 738 (e.g., reconciles) the account information matchingwith payment identifier received in an electronic statement downloadfrom second entity as show in function 740.

The unique identifier and the payment identifier may be generated asnumeric strings, alpha-numeric strings, or any suitable uniquelyidentifiable code. In some embodiments, one or more of the uniqueidentifier and the payment identifier are generated as alpha-numericstrings of at least sixteen characters. In some instances, one or moreof the unique identifier and the payment identifier are sequential,building on previous identifiers while maintaining a unique string. Insome instances, a portion of an identifier indicates the second serverof the second domain 706 and correlates the data movement request withthe second server of the second domain 706. For example, three digits ofthe identifier may be contain a dedicated code for the second server ofthe second domain 706.

FIG. 8 is a flowchart of an example method 800 for facilitating datamovement request presentment, data movement, and reconciliationservices. Operations in the method 800 may be performed by the datamanagement system 100 using modules and components described above withrespect to FIG. 5 and hardware described below with respect to FIG. 10.

In various embodiments, the method 800 may be initiated with anoperation 805. In operation 805, the login module 142 in cooperationwith one or more of the verification module 550, the presentation module570, and the communication module 580 causes presentation of one or moreuser interface elements enabling a user of a client device (e.g., theclient device 480, the first device 702, the second device 710) to inputinformation and register with one or more of the data management system100, the first entity 704, and the second server of the second domain706. The information input into the one or more user interface elementsmay include demographic information, identification information, orsecond entity information associated with the user. The login module 142and one or more of the verification module 550, the presentation module570, and the communication module 580 performs the operation 805 toregister a second user (e.g., second user or the second device 710) andthe first user's profile on the data management system 100 with a firstentity (e.g., first entity 704) and a second server of a second domain(e.g., payment service 706). The registration process enables the datamanagement system 100 to track and reconcile data movement requestsreceived at the data management system 100 for presentation to the firstentity (e.g., first entity) and receive the movement response of thedata movement request from one or more of the first entity, the secondentity, or the second server of the second domain.

In some embodiments, the operation 805 is performed in a graphical userinterface of the data management system 100 after the second device 710transmitted one or more login credentials to the data management system100. After registering with one or more of the first entity 704 and thesecond entity 708, the data management system 100 may automaticallydownload transaction records from the second entity 708 into the userprofile of the data management system 100 and receive transactionnotifications from the first entity 704. In some instances, the datamanagement system 100 may download only indications of the transactions,such as an amount of each transaction, a date of each transaction, andan identifier for each transaction. The data management system 100 mayautomatically reconcile previous data movement requests with one or moreof the transaction records or present the transaction records for manualreconciliation for past data movement requests.

In operation 810, the receiver module 510 receives a data movementrequest. The data movement request has a first status indicatorrepresentative of a status of the data movement request of the datamovement request. The first status indicator represents an unfulfilledstatus of the data movement request (e.g., an unpaid payment status) ofthe data movement request. The receiver module 510 may receive the datamovement request from the second device 710 of the second user. Thereceiver module 510 may receive an indication of the second userselecting to generate the data movement request via interaction with thesecond device 710. In these instances, the receiver module 510 may passthe request to generate the data movement request to one or more modulesof the data management system 100 or the second device 710 to generatethe data movement request. Where the second device 710 generates thedata movement request, the second device 710 transmits the data movementrequest back to the data management system 100. Once the data movementrequest has been received by the receiver module 510, the data movementrequest is stored in the database 270 of the data management system 100.In some instances, the data movement request is associated with one ormore profile of the first user and the second user, such thatmodifications of the data movement request or status of the datamovement request may be reflected with one or more notificationspresented at the second device 710 and the first device 702.

In various example embodiments, to create an data movement request, thesecond device 710 presents a user interface including selectable userinterface elements configured to generate the data movement request withsuitable information for processing by the data management system 100and the data reconciliation system 505. For example, the second device710 may present a create invoice button, operable (e.g., by the seconduser) to create an data movement request. Upon selection of the createdata movement request button (e.g., invoice button), the second device710 presents a series of user interface screens and user interfaceelements requesting information including a total amount for the datamovement request, a name of the customer (e.g., the first user), a typeof invoice, a logo for the business of the second user, an upload dataentry field for uploading an image representative of the logo of thebusiness, data entry fields for mailing addresses of each of the firstuser and the second user, billing information (e.g., a billing accountnumber, a payable bank account, etc.), a metadata field for metadataregarding the data movement request, and item detail data. The metadatafield may include fields for an invoice number, a reference name, agoods and services tax (GST) number, an issued date, and a due date. Theitem detail data may include an item description, a quantity, a unitprice, and an amount.

In operation 820, the code management module 520 appends a uniquerequest code to the data movement request. In various exampleembodiments, the code management module 520 generates the unique requestcode, in response to receiving the data movement request, prior toappending the unique request code to the data movement request. The codemanagement module 520 may append the unique request code to apredetermined portion of instructions configured to represent the datamovement request in a user interface. The code management may append theunique request code to the data movement request within metadataassociated with the data movement request or within the instructionsrepresentative of the data movement request. In some embodiments, theinstructions or the metadata may be exposed to an API of the datamanagement system 100, enabling one or more of the metadata and theinstructions to be opened and modified to include the unique requestcode. The unique request code may be presented to the user in a userperceivable format within a graphical representation of the datamovement request.

In some example embodiments, the unique request code does not identifythe specific data movement request. For example the unique request codemay be an account identification for the second user of the datamanagement system 100 or the second device 710 associated with thesecond user. In these embodiments, the data movement request may have arequest identification number in addition to the unique request code.The data management system 100 may use the unique request code (e.g.,the account identification) to track the progress of the data movementrequest and data provision (e.g., payment) of the data movement requestwithin the first entity 704 and the second server of the second domain706 and provide status modifications, notifications, and other datamovement request tracking operations within the data management system100 and to the second device 710. In this manner, requests, responses,and notifications among the first entity 704, the second server of thesecond domain 706, and the second entity 708, routed to the datamanagement system 100 with the associated account identification (e.g.,unique request code) may serve as an automated reconciliation system togenerate account records within the data management system 100 to beassociated with the accounts of the first user and the second user.

In operation 830, the presentation module 570 causes presentation of thedata movement request at the first device 702 of the first user. Invarious embodiments, the data movement request is presented during anetwork based communication session with the second server of the seconddomain 706 or in a user session of the data management system 100. Wherethe data movement request is presented in the network basedcommunication session, the data movement request may initially bepresented at the first device 702 within a browser and withoutnavigating away from the network based communication session. Where thedata movement request is presented during a communication session of thedata management system 100 and the first device 702, the data managementsystem 100 may cause the first device 702 (e.g., the client device 480shown in FIG. 6) to present the data movement request in a dedicatedapplication, an email, an online user session, or any other suitableuser session. Where presented as an email, a link contained in the emailmay, when selected as a user selectable element presented in a graphicaluser interface, automatically cause a web browser or application to openand prompt entry of user login credentials to view the data movementrequest. Once in the communication session, the data management system100 may cause presentation of one or more of a data movement requestidentifier, a unique URL associated with the data movement request, andone or more detail information of the data movement request (e.g.,currency amounts, services rendered, or goods purchased).

In some instances, the data movement request is presented in acommunication outside the network based communication session. Forexample, the data movement request and unique request code may bepresented at the first device 702 in the form of an email. In someembodiments, the unique request code may form a link to the secondserver of the second domain 706 or the first entity 704. Selecting thelink within the email presented at the first device 702 may cause thefirst device 702 of the first user to be directed to transmit logincredentials. For example, the link may cause the first device 702 topresent directions for the first user to sign in for a network basedcommunication session with the first entity 704 or the second server ofthe second domain 706. The first device 702 may transmit logincredentials to the network based communication session to causepresentation of additional information related to the data movementrequest or make a payment for the data movement request.

In various embodiments, the data movement request includes a paymentlink. The payment link may include a link to the second server of thesecond domain 706. Upon selection of the payment link, the first device702 present a user interface prompt for an identification of the firstentity 704. Upon selection of the identification of the first entity 704the browser of the first device 702 of the first user is directed to asecond server of the second domain (e.g., the payment service 706) of aplurality of second servers. The second server of the plurality ofsecond servers is a second server which supports the first entity 704.In addition to directing the browser of the client device to theselected second servers, selecting the first entity 704 mayautomatically populate payment information required by the selectedsecond server 706 to perform a transaction in response to the datamovement request. In various example embodiments, the data movementrequest prepopulates an identifier for one or more of the data movementrequest (e.g., the unique request code, the request identifier, theaccount identification) and the first user or first device 702; anamount of the invoice (e.g., a total amount of the invoice, a minimumpayment, etc.); and identification of the second user or second device710. The first device 702 may then receive selection of a payment button(e.g., a user interface element) to instruct the second server 706 toprocess the payment among the first entity 704 and the second entity708.

In operation 840, the movement module 530 receives a movement responsevia the network based communication session. In some instances, themovement response includes payment transaction details indicative of apayment received from the client device by the second server 706. Themovement response may be generated by one or more of the first entity704 and the second server 706. Where generated by the first entity 704,the movement response is an indication that the payment has beenforwarded to the second server 706. In these embodiments, the movementresponse is forwarded, along with payment instructions to the secondserver 706 for further processing of the movement response and thepayment instructions. Where the movement response is generated by thesecond server 706, the movement response is generated in response toreceiving payment instructions from the first entity 704.

The payment transaction may extend between two or more of the secondentity 708, the first entity 704, and the second server 706. In someembodiments, when the payment transaction is processed between the firstentity 704 and the second entity 708, the data management system 100 mayreceive a notice of the payment (e.g., the movement response) based onregistration of one or more of the user and the data management system100 with the first entity 704 or the second server 706. In someembodiments, when the first entity 704 transmits payment to the secondentity 708, the transmission of payment causes a payment server of thefirst entity 704 to parse one or more notification tables to determineone or more entities to whom the movement response will be transmitted.In some instances, registration of the user with the first entity 704through the data management system 100 causes the payment server toidentify the data management system 100 as a recipient of the movementresponse. The registration of the user with the first entity 704 may beachieved through one or more of the functions 712 and 714. The movementresponse may be transmitted in response to the function 722, presentingthe ebill to one or more of the second server 706 and the first entity704.

In operation 850, the status module 540 modifies the first statusindicator of the data movement request to a second status indicator toprovisionally reflect the receipt of movement response. In someinstances, after the data movement request (e.g., the notification ofreceipt 734) has been received and stored in the database 270, the datamovement request may include one or more indicator bits. The indicatorbits may be modified by the status module 540 to indicate the currentstatus of the data movement request of the data movement request. Uponreceiving notifications representing changes in the status of the datamovement request, the status module 540 may change the indicator bit,generate a notification of the change in the status of the data movementrequest, and transmit the notification of the change in status of thedata movement request to one or more of the first device 702 and thesecond device 710. As described in operation 850, the status module 540may perform multiple modifications to the indicator bits based ontransaction stages. In some instances, a modification, such as thechange from the first status indicator to the second status indicator,may be understood as a provisional change reflecting an expectation of afurther modification of the status indicator. For example, the statusmodule 540 may change the indicator bit to a value indicating an datamovement request has been partially paid (e.g., a provisional change) orpaid (e.g., the further modification of the status indicator.).

In operation 860, the verification module 550 verifies the movementresponse from a payment receipt. Verifying the movement response may beunderstood as reconciling a banking record with the data movementrequest. In various example embodiments, the operation 860 contains oneor more further operations. For example, as shown in FIG. 8, inoperation 862, the verification module 550 transmits a batch datamovement request to one or more of the second entity 708 (e.g., a bankassociated with a recipient of the payment, the second server 706) andthe primary data center 410. The batch data movement request may betransmitted to the second entity 708, the second server 706, or theprimary data center 410 via the communication module 580 and the network455. For example, in some embodiments, the batch data movement requestmay be transmitted to the primary data center 410 for processing androuting to the second server 706 or the second entity 708. In someinstances, the primary data center will determine payment reconciliationprior to responding to the verification module 550.

In operation 864, the verification module 550 receives confirmation ofthe data movement from one or more entity. In some embodiments, the datamovement may be a payment for which confirmation is received and the oneor more entity may be a financial institution. For example, theverification module 550 may receive confirmation from the first entity704, the second entity 708, the second server 706, or the primary datacenter 410. The confirmation may be in the form of a statement of datamovement (e.g., a set of transactions falling within a specified date),a payment query response, or any other suitable confirmation. Where theverification module 550 receives confirmation from the first entity 704,the first entity 704 may transmit an indication that funds have beendeducted from the first user account. Where the verification module 550receives confirmation from the second entity 708, the second entity 708may transmit an indication that funds have been received into the seconduser account. Where the verification module 550 receives confirmationfrom one or both of the second server 706 or the primary data center410, the second server 706 may indicate a completion of processing thepayment through the second server 706. The primary data center 410 mayprovide confirmation that one or more of the second entity 708, thefirst entity 704, and the second server 706 has performed the abovedescribed actions.

In some embodiments, in operation 864, the receiver module 510 receivesa bank statement from the second entity 708 as confirmation of thepayment form one or more financial institution. The receiver module 510may receive the bank statement in response to the batch data movementrequest. The bank statement is a statement of data movement for thesecond user and may include one or more of payee account information,payer account information, the payment identifier, the uniquetransaction identifier, and other transaction details. In someinstances, the payment identifier may be stored in an ACH field. Invarious embodiments, the bank statement is a statement response in theform of an XML document or other structured data format.

The receiver module 510 may pass the bank statement to the verificationmodule 550. In response to receiving the bank statement and without userinteraction, the verification module 550 matches the bank statement tothe data movement request. In some instances, the verification module550 reconciles the account information with the bank statement bymatching the payment identifier received in the electronic bankstatement with the unique identifier for the data movement request. Theverification module 550 may identify the payment identifier within thebank statement stored in the ACH field, parse the payment identifier,and parse one or more unique identifiers included within data movementrequests associated with a payee in the data management system 100. Theverification module 550 may match the payment identifier with one of theone or more unique identifiers by determining the values for a uniqueidentifier and the payment identifier are identical.

In embodiments where the verification module 550 receives confirmationfrom the second server 706 and the bank statement from the second entity708. The verification module 550 matches the data movement request tothe bank statement and the confirmation from the second server 706 toreconcile the account information with the bank statement and theconfirmation from the second server 706. In some instances, theverification module 550 automatically parses the bank statement and theconfirmation from the second server 706 and compares information parsedfrom the bank statement and the confirmation with the data movementrequest to match the payment identifier in the electronic bank statementand the payment identifier in the confirmation with the uniqueidentifier for the data movement request.

FIG. 9 is a flowchart of an example method 900 for facilitating datamovement request processing and payment reconciliation. Operations ofthe method 900 may be performed by the data management system 100 usingmodules and components described above with respect to FIG. 5 andhardware described below with respect to FIG. 10. As shown in FIG. 9,the method 900 includes one or more operations of the method 800described above.

In some instances, the method 900 is initially performed by operation810. In various example embodiments, the data movement request includesa detail link. The detail link may be understood and implemented as ahyperlink, a network address, or any other suitable link enablingcommunication or contact with the second server. In order to initiatethe communication relating to the detail link, the first device 702receives a selection of the detail link in a user interfacerepresentation of the data movement request. The detail link isconfigured to direct a browser of the client device to requesttransaction detail information from the server via the network, thetransaction detail information including transaction information for thedata movement request.

In operation 910, the movement module 530 transmits the data movementrequest (e.g., the data movement request for the payer), including theunique data movement request code and the detail link, to the secondserver 706 for presentation during the network based communicationsession. The movement module 530 may transmit the data movement request,the unique request code, and the detail link using the communicationmodule 580 via the network 455.

In various example embodiments, the transmission of the data movementrequest, unique request code, and the detail link is in response toreceiving a request for ebill or data movement request information fromthe first device 702, via the first entity 704, to one or more of thesecond server 706 and the data management system 100. For example, therequest for ebill is received by the second server 706 and transmittedto the data management system 100 storing the data movement request,unique request code, and detail link. In return, the data managementsystem 100 transmits the ebill (e.g., the data movement request, theunique request code, and the detail link) to the second server 706 forpresentation at the first device 702.

In operation 920, in response to receiving a request for transactiondetail, the presentation module 570 causes presentation of the datamovement request, the unique request code, and further transactiondetail information at the first device 702 associated with the firstuser. The request for transaction detail may be in the form of the firstdevice 702 receiving a selection of the detail link within the datamovement request in the network based communication session andgenerating an indication of the selection as the request for transactiondetail. Selection of the detail link may cause the client device totransmit a request to the second server 706 for forwarding to the datamanagement system 100. In response to the request, the transactiondetail information may be transmitted to the second server 706 from thedata management system 100. The transaction detail may include the datamovement request, time of data movement request, itemized charges, goodsor services received, and other pertinent information stored on the datamanagement system 100. In various example embodiments, causingpresentation of the transaction detail information is performed byproviding the transaction detail information as presented during thenetwork based communication session without navigating away from orinterrupting the network based communication session. In some instances,the detail link may navigate or otherwise direct the client devicebrowser to, or open a new window directed to, the data management system100 for presentation of the transaction detail.

In operation 930, the movement module 530 receives a presentationnotification from the second server 706. The presentation notificationis indicative of presentation of at least the data movement request andunique request code at the client device during the network basedcommunication session. The presentation notification may be automatedsuch that when the data movement request is presented at the firstdevice 702 on the client device, the client device transmits a responsethrough the second server 706 to the data management system 100indicative of the presentation. The presentation notification may be inthe form of user interface instructions configured to generate a userperceivable notification, instructions configured to change a status orother portion of the data movement request on the database 270 of thedata management system 100, or any other suitable presentationnotification. In some instances, the presentation notification may beforwarded to the second device 710 or otherwise indicated in a profileof the second user.

In various example embodiments, after receiving the movement response inoperation 840, the movement module 530, in operation 940, generates anotification of receipt, the notification containing confirmation ofreceipt of the movement response from the second server 706. In someembodiments, where the movement response is an indication of payment,the notification may be a notification of payment received from apayment service in the form of the second server 706. The notificationof receipt may be generated in response to the first device 702interacting with the first entity 704 in the network based communicationsession to set up a payment for the data movement request.

In some instances, the first entity 704 may generate a paymentinstruction, after interaction with the first device 702. The firstentity 704 may then transmit the payment instruction to the secondserver 706. After receiving the payment instruction, the second server706 may execute the payment instruction against the first user's accountat the first entity 704 and transmit the funds, along with a paymentidentification to the second entity 708. The second server 706 may alsoinclude the payment identification and the unique request code in themovement response transmitted to the data management system 100. Thedata management system 100 may store the movement response in thedatabase 270 and associate the movement response with the data movementrequest.

In operation 950, the movement module 530 transmits the notification ofreceipt, including the payment identification and the unique requestcode, to the second device 710 of the second user via the network 455.In some instances, the movement module 530 may also transmit thenotification of receipt to the first device 702 of the first user as aconfirmation of the payment transaction.

In some embodiments, at least a portion of the method 900 may be furtherperformed in the operation 850, by modifying the first status indicator,and the operation 860, by verifying the movement response. In operation960, in response to verifying the movement response, the status module540 modifies the second status indicator to a third status indicator toreflect the verification of the movement response for the data movementrequest. The status module 540 may modify the data movement requestwithin the database 270 and information relating to the data movementrequest in one or more of the profiles of the first user and the seconduser. In these embodiments, the first device 702 and the second device710 may receive a final notification of the status of the data movementrequest and the status module 540 may close a transaction represented bythe data movement request.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., processor executable instructions embodied on anon-transitory machine-readable storage medium or in a transmissionsignal) or hardware modules. A hardware module is a tangible unitcapable of performing certain operations and may be configured orarranged in a certain manner. In example embodiments, one or morecomputer systems (e.g., a standalone, client, or server computer system)or one or more hardware modules of a computer system (e.g., a processoror a group of processors) may be configured by software (e.g., anapplication or application portion) as a hardware module that operatesto perform certain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired) or temporarilyconfigured (e.g., programmed) to operate in a certain manner and/or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation, and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or more processors orprocessor-implemented modules. The performance of certain of theoperations may be distributed among the one or more processors, not onlyresiding within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a SaaS.For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., APIs).

Example embodiments may be implemented in digital electronic circuitry,or in computer hardware, firmware, software, or in combinations of them.Example embodiments may be implemented using a computer program product,e.g., a computer program tangibly embodied in an information carrier,e.g., in a machine-readable medium for execution by, or to control theoperation of, data processing apparatus, e.g., a programmable processor,a computer, or multiple computers.

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, subroutine,or other unit suitable for use in a computing environment. A computerprogram can be deployed to be executed on one computer or on multiplecomputers at one site or distributed across multiple sites andinterconnected by a communication network.

In example embodiments, operations may be performed by one or moreprogrammable processors executing a computer program to performfunctions by operating on input data and generating output. Methodoperations can also be performed by, and apparatus of exampleembodiments may be implemented as, special purpose logic circuitry(e.g., a FPGA or an ASIC).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. Inembodiments deploying a programmable computing system, it will beappreciated that that both hardware and software architectures requireconsideration. Specifically, it will be appreciated that the choice ofwhether to implement certain functionality in permanently configuredhardware (e.g., an ASIC), in temporarily configured hardware (e.g., acombination of software and a programmable processor), or a combinationof permanently and temporarily configured hardware may be a designchoice. Below are set out hardware (e.g., machine) and softwarearchitectures that may be deployed, in various example embodiments.

FIG. 10 is a block diagram of a machine in the example form of acomputer system 1000 within which instructions, for causing the machineto perform any one or more of the methodologies discussed herein, may beexecuted. In alternative embodiments, the machine operates as astandalone device or may be connected (e.g., networked) to othermachines. In a networked deployment, the machine may operate in thecapacity of a server or a client machine in server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine may be a personal computer (PC), atablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), acellular telephone, a web appliance, a network router, switch or bridge,or any machine capable of executing instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

Example computer system 1000 includes a processor 1002 (e.g., a centralprocessing unit (CPU), a graphics processing unit (GPU), or both), amain memory 1004, and a static memory 1006, which communicate with eachother via a bus 1008. Computer system 1000 may further include a videodisplay device 1010 (e.g., a liquid crystal display (LCD) or a cathoderay tube (CRT)). Computer system 1000 also includes an alphanumericinput device 1012 (e.g., a keyboard), a user interface navigation device1014 (e.g., a mouse or touch sensitive display), a disk drive unit 1016,a signal generation device 1018 (e.g., a speaker), and a networkinterface device 1020.

Disk drive unit 1016 includes a machine-readable medium 1022 on which isstored one or more sets of instructions and data structures (e.g.,software) 1024 embodying or utilized by any one or more of themethodologies or functions described herein. Instructions 1024 may alsoreside, completely or at least partially, within main memory 1004,within static memory 1006, and/or within processor 1002 during executionthereof by computer system 1000, with main memory 1004 and processor1002 also constituting machine-readable media.

While machine-readable medium 1022 is shown in an example embodiment tobe a single medium, the term “machine-readable medium” may include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore instructions or data structures. The term “machine-readable medium”shall also be taken to include any tangible medium that is capable ofstoring, encoding or carrying instructions for execution by the machineand that cause the machine to perform any one or more of themethodologies of the present technology, or that is capable of storing,encoding or carrying data structures utilized by or associated with suchinstructions. The term “machine-readable medium” shall accordingly betaken to include, but not be limited to, solid-state memories, andoptical and magnetic media. Specific examples of machine-readable mediainclude non-volatile memory, including by way of example semiconductormemory devices, e.g., Erasable Programmable Read-Only Memory (EPROM),Electrically Erasable Programmable Read-Only Memory (EEPROM), and flashmemory devices; magnetic disks such as internal hard disks and removabledisks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

Instructions 1024 may further be transmitted or received over acommunications network 1026 using a transmission medium. Instructions1024 may be transmitted using network interface device 1020 and any oneof a number of well-known transfer protocols (e.g., HTTP). Examples ofcommunication networks include a local area network (LAN), a wide areanetwork (WAN), the Internet, mobile telephone networks, Plain OldTelephone (POTS) networks, and wireless data networks (e.g., WiFi andWiMAX networks). The term “transmission medium” shall be taken toinclude any intangible medium that is capable of storing, encoding orcarrying instructions for execution by the machine, and includes digitalor analog communications signals or other intangible media to facilitatecommunication of such software.

Although an embodiment has been described with reference to specificexample embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thescope of the technology. Accordingly, the specification and drawings areto be regarded in an illustrative rather than a restrictive sense. Theaccompanying drawings that form a part hereof, show by way ofillustration, and not of limitation, specific embodiments in which thesubject matter may be practiced. The embodiments illustrated aredescribed in sufficient detail to enable those skilled in the art topractice the teachings disclosed herein. Other embodiments may beutilized and derived therefrom, such that structural and logicalsubstitutions and changes may be made without departing from the scopeof this disclosure. This Detailed Description, therefore, is not to betaken in a limiting sense, and the scope of various embodiments isdefined only by the appended claims, along with the full range ofequivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

What is claimed is:
 1. A method for automated reconciliation, comprising: receiving, by one or more processor of a first server of a first domain, a first data movement request having a first status indicator for the first data movement request; automatically appending, by the one or more processor of the first server, a unique request code to the first data movement request; transmitting the first data movement request and the unique request code to a server associated with a first entity; automatically presenting the first data movement request at a client device associated with the first entity during a network-based communications session between the first server and a second server of a second domain; automatically receiving, by the one or more processor of the first server, a movement response from the second server via the network-based communications session, the movement response indicating a first interaction between the server associated with the first entity and the second server and a second interaction between the second server and a third server of a third domain, the second interaction being performed by the second server in response to the first interaction; automatically modifying the first status indicator of the first data movement request to a second status indicator reflecting receipt of the movement response; and automatically verifying, by the first server, an indication of movement between the server associated with the first entity and the third server, the verifying comprising: transmitting a second data movement request to the third server; receiving, by the first server, a confirmation notification including a data movement statement and the unique request code; and matching a portion of the data movement statement of the confirmation notification to a portion of the first data movement request.
 2. The method of claim 1, wherein the first status indicator is representative of an unreconciled status of the first data movement request.
 3. The method of claim 1, further comprising: responsive to the receiving of the first data movement request, generating the unique request code.
 4. The method of claim 1, further comprising: transmitting the first data movement request and the unique request code to the second server for presentation during the network-based communications session.
 5. The method of claim 1, wherein the first data movement request includes a detail link, the detail link configured to direct a browser of the client device to request transaction detail information from the first server via a network, the transaction detail information including transaction information for the first data movement request.
 6. The method of claim 5, further comprising: responsive to receiving a request for transaction detail from the detail link, causing presentation of the first data movement request, the unique request code, and the transaction detail information at the client device.
 7. The method of claim 6, wherein causing presentation of the transaction detail information further comprises: transmitting the transaction detail information to the second server, the transaction detail information configured to be provided by the second server and displayed at the client device during the network-based communications session.
 8. The method of claim 1, further comprising: receiving a presentation notification from the second server, the presentation notification indicating presentation of the first data movement request and unique request code at the client device during the network-based communications session.
 9. The method of claim 1, wherein the movement response includes transmission details indicative of a data payload received from the client device by the second server.
 10. The method of claim 1, further comprising: generating a notification of receipt containing confirmation of receipt of the movement response from the second server; and transmitting, by the second server, the notification of receipt to the client device via a network.
 11. The method of claim 1, wherein the verifying of the indication of movement further comprises: transmitting a batch second data movement request to a batch server associated with a recipient of data associated with the first data movement request and the second domain; and receiving, at the first server, a movement notification including a statement of data movement and the unique request code, the movement notification being confirmation of the data associated with the first data movement request being received by the batch server.
 12. The method of claim 1, further comprising: responsive to the verifying of the movement response, modifying the second status indicator to a third status indicator reflecting the verification of the movement response for the first data movement request.
 13. A system, comprising: a memory having instructions embodied thereon; one or more processors configured by the instructions to perform operations comprising: receiving, by one or more processor of a first server of a first domain, a first data movement request having a first status indicator for the first data movement request; automatically appending, by the one or more processor of the first server, a unique request code to the first data movement request; transmitting the first data movement request and the unique request code to a server associated with a first entity; automatically presenting the first data movement request at a client device associated with the first entity during a network-based communications session between the first server and a second server of a second domain; automatically receiving, by the one or more processor of the first server, a movement response from the second server via the network-based communications session, the movement response indicating a first interaction between the server associated with the first entity and the second server and a second interaction between the second server and a third server of a third domain, the second interaction being performed by the second server in response to the first interaction; automatically modifying the first status indicator of the first data movement request to a second status indicator reflecting receipt of the movement response; and automatically verifying, by the first server, an indication of movement between the server associated with the first entity and the third server, the verifying comprising: transmitting a second data movement request to the third server; receiving, by the first server, a confirmation notification including a data movement statement and the unique request code; and matching a portion of the data movement statement of the confirmation notification to a portion of the first data movement request.
 14. The system of claim 13, wherein the first data movement request includes a detail link configured to direct a browser of the client device to request transaction detail information from the first server via a network, the transaction detail information including transaction information for the first data movement request.
 15. The system of claim 14, wherein the operations further comprise: responsive to receiving a request for transaction detail from the detail link, causing presentation of the first data movement request, the unique request code, and the transaction detail information at the client device.
 16. The system of claim 15, wherein the operations further comprise: transmitting the transaction detail information to the second server, the transaction detail information configured to be provided by the second server and displayed at the client device during the network-based communications session.
 17. The system of claim 13, wherein the operations further comprise: generating a notification of receipt containing confirmation of receipt of the movement response from the second server; and transmitting, by the second server, the notification of receipt to the client device via a network.
 18. The system of claim 17, wherein the operations further comprise: transmitting a batch second data movement request to a batch server associated with a recipient of the data associated with the first data movement request and the second domain; and receiving, at the first server, a movement notification including a statement of data movement and the unique request code, the movement notification being confirmation of the data associated with the first data movement request being received by the batch server; and reconciling a data transaction with the statement of data movement and the movement response using the data transaction, the unique request code, and the notification of receipt.
 19. A non-transitory machine-readable storage medium comprising processor executable instructions that, when executed by a processor of a machine, cause the machine to perform operations comprising: receiving, by one or more processor of a first server of a first domain, a first data movement request having a first status indicator for the first data movement request; automatically appending, by the one or more processor of the first server, a unique request code to the first data movement request; transmitting the first data movement request and the unique request code to a server associated with a first entity; automatically presenting the first data movement request at a client device associated with the first entity during a network-based communications session between the first server and a second server of a second domain; automatically receiving, by the one or more processor of the first server, a movement response from the second server via the network-based communications session, the movement response indicating a first interaction between the server associated with the first entity and the second server of the second domain and a second interaction between the second server of the second domain and a third server of a third domain, the second interaction being performed by the second server in response to the first interaction; automatically modifying the first status indicator of the first data movement request to a second status indicator reflecting receipt of the movement response; and automatically verifying, by the first server, an indication of movement between the server associated with the first entity and the third server, the verifying comprising: transmitting a second data movement request to the third server; receiving, by the first server, a confirmation notification including a data movement statement and the unique request code; and matching a portion of the data movement statement of the confirmation notification to a portion of the first data movement request.
 20. The non-transitory machine-readable storage medium of claim 19, wherein the operations further comprise: generating a notification of receipt containing confirmation of receipt of the movement response from the second server; and transmitting, by the second server, the notification of receipt to the client device via a network. 